[release/10.0] Pass container image correctly for source-build job in official build #64779
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
1ES PT expects an object with the container image, not just the name. Use the same azureLinux30Net10BuildAmd64 container as we do in other jobs since we only build managed code.
akoeplinger
added
tell-mode
Contributor
|
Hey @dotnet/aspnet-build, looks like this PR is something you want to take a look at. |
akoeplinger
approved these changes
Dec 16, 2025
Contributor
|
Looks like this PR hasn't been active for some time and the codebase could have been changed in the meantime. |
dotnet-policy-service
bot
added
the
pending-ci-rerun
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport of #64770 to release/10.0
/cc @akoeplinger
Pass container image correctly for source-build job in official build. We accidentally built on the host instead of in the container like we thought which caused an issue when the host image was bumped to one that doesn't ship
azCLI.